Release 10.1A: OpenEdge Development:
Debugging and Troubleshooting

Abnormal termination dump files

An abnormal termination can result in some combination of the following dump files:

procore file
protrace file
core file
Note: To analyze the contents of a protrace file, you need the assistance of Progress Software Corporation Technical Support.

procore file

A procore file is a text file that contains:

A list of recent messages, by message number.
A 4GL procedure stack trace that includes line numbers from the debug listing file within each procedure.

Progress writes the procore file to a temporary directory, if you specify the Temporary Directory (-T) startup parameter; otherwise, Progress writes the procore file to the current working directory.

Example 7–1 is a sample procore file.

Example 7–1: Sample procore file  

_12/18/01 13:44:57 [784] Progress Recent Message(s): (5635) (5407) (5407) (5407) (5407) (5407) (5407) (5407) (5407) (5407) *** 4GL Call Stack *** 4: foo InfiniteLoop.p (InfiniteLoop.p) 4: foo InfiniteLoop.p (InfiniteLoop.p) 4: foo InfiniteLoop.p (InfiniteLoop.p) 4: foo InfiniteLoop.p (InfiniteLoop.p) 4: foo InfiniteLoop.p (InfiniteLoop.p) 4: foo InfiniteLoop.p (InfiniteLoop.p) ... (many more of these) ... 1: InfiniteLoop.p (InfiniteLoop.p) 1: D:\pcspot\dir1\p89453r.ped (D:\pcspot\dir1\p89453r.ped) 588: adecomm/_runcode.p (adecomm/_runcode.r) 3796: ExecuteRun adeedit/_proedit.p (adeedit/_proedit.r) 10550: RunFile adeedit/_proedit.p (adeedit/_proedit.r) 2323: USER-INTERFACE-TRIGGER adeedit/_proedit.p (adeedit/_proedit.r) 11727: adeedit/_proedit.p (adeedit/_proedit.r) 453: _edit.p (\\ruddles\i_91d_nt\dlc\gui\_edit.r)

This resulted from running a program in the Procedure Editor that contains an infinite loop. Line numbers appear at the beginning of a line, followed by a colon.

protrace file

A protrace file is a text file that contains:

A C stack trace.
Symbolic information (when available).

Progress writes the protrace file to the current directory. Progress cannot properly generate the protrace file on some UNIX versions, such as AIX.

Example 7–2 is a sample protrace file.

Example 7–2: Sample protrace file  

//===================================================== PROGRESS stack trace as of Mon Nov 12 11:47:40 2001 //===================================================== Exception code: C0000005 ACCESS_VIOLATION Fault address: 10002E92 01:00001E92 D:\stern\v91\progress\wdbg\prow32.dll Registers: EAX:00000000 EBX:00000000 ECX:104353E4 EDX:10435430 ESI:00000014 EDI:00050000 CS:EIP:001B:10002E92 SS:ESP:0023:0012F0E0 EBP:0012F10C DS:0023 ES:0023 FS:0038 GS:0000 Flags:00010202 Call Stack: Address Frame 10002E92 0012F10C datein+40A 1000299E 0012F13C fminpt+19D 102B945A 0012F164 smginit+B7 102B6531 0012F664 smdefnreal+2CCF 102B385E 0012F674 smdefn+D 102E0830 0012F6DC smstmt+DAB 103D9A45 0012F858 smsem+11E8 10190274 0012F898 crpsrch+1322 1018F7CB 0012FE68 crpsrch+879 1018E989 0012FEC0 crrun_entry+13E 1018E1BF 0012FECC rninterpret+30 1001E3FD 0012FED8 rnrq+E5 1000A81E 0012FF08 drmain+20F 100528B4 0012FF1C ProStartup+5F 00401008 0012FF24 WinMain+8 00401148 0012FFC0 WinMainCRTStartup+134 77F1BA06 0012FFF0 BaseComputeProcessDllPath+18A

Note: To analyze the contents of a protrace file, you need the assistance of Progress Software Corporation Technical Support.

core file

A core file is specific to UNIX. It is a binary file that requires a UNIX debugger such as dbx. A core file contains:

A C stack trace.
Hex representation of the parameters to each routine.

On some systems, an executable’s permissions do not allow core file generation.